Why travis failed in master branch, but successed in PR

wsdjeg · September 13, 2020, 2:01am

I think this is a bug, because all the configuration is same in PR and master branch. It successed in PR, but failed in master branch without useful infomation:

the PR job is: https://travis-ci.org/github/SpaceVim/SpaceVim/jobs/726594076

the master job is: https://travis-ci.org/github/SpaceVim/SpaceVim/jobs/726584968

I want to know is there any differences between the master branch building and pr building?

BanzaiMan · September 14, 2020, 2:32pm

I am highly skeptical that this is a bug on our end.

Your script

github.com

SpaceVim/SpaceVim/blob/a22284b4fb7ce297dd1747a425052b9f088fad21/.ci/script.sh#L3


#!/usr/bin/env bash

set -ex
export TRAVIS_PULL_REQUEST=${TRAVIS_PULL_REQUEST}
if [ "$LINT" = "vimlint" ]; then
    if [[ -f build_log ]]; then
        rm build_log
    fi
    for file in $(git ls-files | grep SpaceVim.*.vim);
    do
        /tmp/vimlint/bin/vimlint.sh -l /tmp/vimlint -p /tmp/vimlparser $file >> build_log 2>&1;
    done
    if [[ -s build_log ]]; then

is setting errexit, and it is failing with the first command that exits with nonzero. It is hard for me to say what is causing the problem, but you are the best person to trouble shoot that issue.

You may also have stale cache, in which case deleting it can help you sort out the issue.

Additionally, we can turn on the debug feature if you are interested.

native-api · September 14, 2020, 6:07pm

@BanzaiMan I’m more concerned why there’s no “<command> exited with <code>” message in the log after the failed command’s output. Looks like a case of lost output. They produce lots of output after “Writing coverage file .coverage_covimerage.”.

native-api · September 15, 2020, 12:13am

Regarding the OP’s issue, this does seem to be a user script error.

A workaround for losing output is to avoid producing very much output very quickly like the coverage file dump:

then you should be able to see the output from where the error happens and diagnose it.

wsdjeg · September 15, 2020, 3:12am

TThanks for reply. But I do not understand why the PR building sucessed? only branch building is failed. the logic and commands are all same.

native-api · September 29, 2020, 8:49pm

There may be different cache, there may be different set of configuration envvars, there may be external factors or code changes. Impossible to say without seeing the actual error.

wsdjeg · September 30, 2020, 1:52pm

Is it possiable disable all the fuck cache?

Topic		Replies	Views
Duplicate job attempts for PR builds causing "Queued — Build Created" problems Travis CI Discussions & Feedback github-integration	25	1329	October 18, 2020
Commits on master branch showing up with an "x" because a PR is failing Travis CI Discussions & Feedback bug	2	538	September 15, 2019
Build not starting Travis CI Discussions & Feedback	19	3816	March 30, 2020
Build statuses are not per branch in github Travis CI Discussions & Feedback github-integration	1	654	January 23, 2019
Travis-CI stopped tracking/building a PR Travis CI Discussions & Feedback	2	1226	July 10, 2019

Why travis failed in master branch, but successed in PR

Related Topics