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

Fix different test failures #890

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Conversation

bmeneg
Copy link
Collaborator

@bmeneg bmeneg commented Feb 27, 2024

This MR bring different commits to handle different test failures we're seeing on every MR.
Some failures were caused due to the nature of our test cases that run on real/live GitLab repository, but others were caused by previous code changes. At the same time, one was caused by the go version being used in our CI, requiring an update to make it work.

Update go version to fix issues during tests where some tests requires a
specific go version, above 1.17 we had setup for lab.

Signed-off-by: Bruno Meneguele <[email protected]>
Make sure our CI follows the same go version stated in go.mod.

Signed-off-by: Bruno Meneguele <[email protected]>
Fix styling issue reported by gofmt.

Signed-off-by: Bruno Meneguele <[email protected]>
Unfortunately our testing infra relies on a real environment that get
updated from time to time. This commit updates the MR number to match
the test code with the actual MR live in the testing repo.

Signed-off-by: Bruno Meneguele <[email protected]>
@bmeneg bmeneg changed the title mod: update go version Fix different test failures Feb 27, 2024
cmd/mr_discussion.go Outdated Show resolved Hide resolved
With commit 4d1dbfa ("cmd/mr_discussion.go: Switch from NotePosition to
PositionOptions") the PositionOptions object was being created
regardless the presence of --position in user's command, causing the
REST API to fail due to the presence of a "position" parameter in the
request without all required arguments. This commit creates the
PositionOptions object within the --position handler, ensuring it's not
passed "empty".

Signed-off-by: Bruno Meneguele <[email protected]>
Due to a minimal change in tview library an additional char was added
when printing the stage and jobs to the terminal. Unfortunately these
tests are too sensitive to this type of changes.

My suggestion is that we remove visual tests from our code, since the
library has their own tests and we should not be worried on how things
are really printed.

Signed-off-by: Bruno Meneguele <[email protected]>
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.

None yet

2 participants