Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests/manual: add in coreos-builds-bisect script #2961

Merged

Conversation

dustymabe
Copy link
Member

This script will allow us to perform bisection on our list of builds for our CoreOS streams. It will enable us to find issues faster. It was inspired by rpm-ostree-bisect [1], which does somethign similar, but operates on the OSTree repo from inside the OS.

Example output looks something like:

+ echo 'Could not access /etc/shadow -> SUCCESS'
Could not access /etc/shadow -> SUCCESS
+ exit 0
38.20230819.3.0 passed
BISECT TEST RESULTS:
Last known good build: 38.20230819.3.0
First known bad build: 38.20230902.3.0

[1] https://github.com/ostreedev/ostree-releng-scripts/blob/master/rpm-ostree-bisecthis

This script will allow us to perform bisection on our list
of builds for our CoreOS streams. It will enable us to find issues
faster. It was inspired by rpm-ostree-bisect [1], which does somethign
similar, but operates on the OSTree repo from inside the OS.

Example output looks something like:

```
+ echo 'Could not access /etc/shadow -> SUCCESS'
Could not access /etc/shadow -> SUCCESS
+ exit 0
38.20230819.3.0 passed
BISECT TEST RESULTS:
Last known good build: 38.20230819.3.0
First known bad build: 38.20230902.3.0
```

[1] https://github.com/ostreedev/ostree-releng-scripts/blob/master/rpm-ostree-bisecthis
Copy link
Member

@jlebon jlebon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't review the script in depth, but it looks sane to me!

Though I wonder if it should be in e.g. tests/tools/ or tests/scripts/ instead? All the other files in tests/manual/ currently are actual scripts that test specific features and so are accurately described by the directory name. This seems like a more generic tool?

@dustymabe
Copy link
Member Author

Though I wonder if it should be in e.g. tests/tools/ or tests/scripts/ instead? All the other files in tests/manual/ currently are actual scripts that test specific features and so are accurately described by the directory name. This seems like a more generic tool?

I don't have a strong opinion there. Mostly the things in here are here because we didn't have a better place to put them and you generally know what you are looking for if you get down this far..

With as few of these that there are I'm not sure making other directories will add value (i.e. compared to the more searching) until we get into maybe 10s of files?

TL;DR Want it in a scripts/ dir? I'll put it there if you think it's worth it.

@jlebon
Copy link
Member

jlebon commented Apr 12, 2024

TL;DR Want it in a scripts/ dir? I'll put it there if you think it's worth it.

Actually yeah, scripts/ is even more appropriate. But no strong opinion either if you want to keep it there.

@dustymabe
Copy link
Member Author

I'll keep it where it is for now just to save a CI cycle. Thanks for the review!

@dustymabe dustymabe merged commit 8989d70 into coreos:testing-devel Apr 12, 2024
3 checks passed
@dustymabe dustymabe deleted the dusty-coreos-builds-bisect branch April 12, 2024 14:24
dustymabe added a commit to dustymabe/coreos-assembler that referenced this pull request May 6, 2024
This will allow one to just specify a build ID rather than having
to specify both the stream the build was on and the build ID. This
will make things slightly more convenient for things like
coreos-builds-bisect [1] where the called script now doesn't need
to know what stream we are on.

[1] coreos/fedora-coreos-config#2961
dustymabe added a commit to dustymabe/coreos-assembler that referenced this pull request May 6, 2024
This will allow one to just specify a build ID rather than having
to specify both the stream the build was on and the build ID. This
will make things slightly more convenient for things like
coreos-builds-bisect [1] where the called script now doesn't need
to know what stream we are on.

[1] coreos/fedora-coreos-config#2961
dustymabe added a commit to coreos/coreos-assembler that referenced this pull request May 7, 2024
This will allow one to just specify a build ID rather than having
to specify both the stream the build was on and the build ID. This
will make things slightly more convenient for things like
coreos-builds-bisect [1] where the called script now doesn't need
to know what stream we are on.

[1] coreos/fedora-coreos-config#2961
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants