Container removal broke a lot of tests #1175

Closed
opened 2025-12-28 17:22:04 +00:00 by sami · 8 comments
Owner

Originally created by @roman-khimov on GitHub (Dec 26, 2023).

Originally assigned to: @carpawell on GitHub.

Expected Behavior

Like before #2638 merge: https://http.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1168-1703535611/index.html

Current Behavior

https://http.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1169-1703535726/index.html

Possible Solution

Fix it.

Steps to Reproduce (for bugs)

Run testcases.

Regression

Yeah, #2638.

Originally created by @roman-khimov on GitHub (Dec 26, 2023). Originally assigned to: @carpawell on GitHub. ## Expected Behavior Like before #2638 merge: https://http.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1168-1703535611/index.html ## Current Behavior https://http.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1169-1703535726/index.html ## Possible Solution Fix it. ## Steps to Reproduce (for bugs) Run testcases. ## Regression Yeah, #2638.
sami 2025-12-28 17:22:04 +00:00
Author
Owner

@cthulhu-rider commented on GitHub (Dec 26, 2023):

what prevents us from tracking tests' breakage before merging?

@cthulhu-rider commented on GitHub (Dec 26, 2023): what prevents us from tracking tests' breakage before merging?
Author
Owner

@roman-khimov commented on GitHub (Dec 26, 2023):

It was ~ok: https://http.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1165-1703509070/index.html

@roman-khimov commented on GitHub (Dec 26, 2023): It was ~ok: https://http.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1165-1703509070/index.html
Author
Owner

@cthulhu-rider commented on GitHub (Dec 26, 2023):

It was ~ok: https://http.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1165-1703509070/index.html

i see, we run only a bit more than 10% of all tests on PRs. Is there a plan to autorun all tests?

@cthulhu-rider commented on GitHub (Dec 26, 2023): > It was ~ok: https://http.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1165-1703509070/index.html i see, we run only a bit more than 10% of all tests on PRs. Is there a plan to autorun all tests?
Author
Owner

@roman-khimov commented on GitHub (Dec 26, 2023):

These are just different modes, PR and master. 2h+ test suite for every push into PR is too expensive.

@roman-khimov commented on GitHub (Dec 26, 2023): These are just different modes, PR and master. 2h+ test suite for every push into PR is too expensive.
Author
Owner

@cthulhu-rider commented on GitHub (Dec 26, 2023):

can PR tests be run when the changes are ready-to-merge (manually, or on approvals) somehow? all tests take some time anyway, so it's better to catch failures in the PR, not within merge-detect-PR-merge-detect-PR... flow

@cthulhu-rider commented on GitHub (Dec 26, 2023): can PR tests be run when the changes are ready-to-merge (manually, or on approvals) somehow? all tests take some time anyway, so it's better to catch failures in the PR, not within merge-detect-PR-merge-detect-PR... flow
Author
Owner

@roman-khimov commented on GitHub (Dec 26, 2023):

Only if https://github.com/nspcc-dev/neofs-node/actions/workflows/run-tests.yml is to be parameterized for that (it autodetects PR/master currently). But you'll forget to run it, don't worry.

@roman-khimov commented on GitHub (Dec 26, 2023): Only if https://github.com/nspcc-dev/neofs-node/actions/workflows/run-tests.yml is to be parameterized for that (it autodetects PR/master currently). But you'll forget to run it, don't worry.
Author
Owner

@cthulhu-rider commented on GitHub (Dec 26, 2023):

forget to run it, don't worry

forget to run - another problem, dont run at all - current

@cthulhu-rider commented on GitHub (Dec 26, 2023): > forget to run it, don't worry forget to run - another problem, dont run at all - current
Author
Owner

@cthulhu-rider commented on GitHub (Dec 28, 2023):

same OKness again https://http.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1176-1703703416/index.html

@cthulhu-rider commented on GitHub (Dec 28, 2023): same OKness again https://http.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1176-1703703416/index.html
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-node#1175
No description provided.