Merge lp:~elopio/snappy/new_kernel_file_name into lp:~snappy-dev/snappy/snappy-moved-to-github
| Status: | Merged |
|---|---|
| Approved by: | Leo Arias on 2015-09-25 |
| Approved revision: | 716 |
| Merged at revision: | 717 |
| Proposed branch: | lp:~elopio/snappy/new_kernel_file_name |
| Merge into: | lp:~snappy-dev/snappy/snappy-moved-to-github |
| Diff against target: |
85 lines (+20/-33) 1 file modified
_integration-tests/tests/failover_zero_size_file_test.go (+20/-33) |
| To merge this branch: | bzr merge lp:~elopio/snappy/new_kernel_file_name |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Federico Gimenez (community) | 2015-09-22 | Approve on 2015-09-25 | |
|
Review via email:
|
|||
Commit Message
On integration tests, fixed newKernelFilena
| Federico Gimenez (fgimenez) wrote : | # |
| Leo Arias (elopio) wrote : | # |
I removed the classic kernel files stuff, and now it's passing in 15.04 and rolling. Please confirm.
| Snappy Tarmac (snappydevtarmac) wrote : | # |
The attempt to merge lp:~elopio/snappy/new_kernel_file_name into lp:snappy failed. Below is the output from the failed tests.
Checking docs
Checking formatting
Formatting wrong in following files
_integration-
# we always run in a fresh dir in tarmac
export GOPATH=$(mktemp -d)
trap 'rm -rf "$GOPATH"' EXIT
# this is a hack, but not sure tarmac is golang friendly
mkdir -p $GOPATH/
cp -a . $GOPATH/
cd $GOPATH/
sh -v ./run-checks
#!/bin/sh
set -eu
if which goctest >/dev/null; then
goctest=
else
goctest="go test"
fi
QUICK=""
if [ "${1:-}" = "--quick" ]; then
QUICK=yes
fi
echo Checking docs
./mdlint.py docs/*.md
echo Checking formatting
fmt=$(gofmt -l .)
if [ -n "$fmt" ]; then
echo "Formatting wrong in following files"
echo "$fmt"
exit 1
fi


Thanks for this, Leo, hopefully we'll get this make this work soon with the new kernel files layout.
I'm getting an error in an installApp test not related to these changes, probably we haven't merged the branch that fixes this yet, let me know if it's an issue for you too:
/home/fgimenez/ workspace/ snappy/ new_kernel_ file_name/ _integration- tests/tests/ installApp_ test.go: 122: workspace/ snappy/ new_kernel_ file_name/ _integration- tests/tests/ installApp_ test.go: no such file or directory canonical\ n" + canonical\ n" + canonical failed to install: snappy package not found\n"
...open /home/fgimenez/
... obtained string = "" +
... "Installing unexisting.
... "unexisting failed to install: snappy package not found\n"
... expected string = "" +
... "Installing unexisting.
... "unexisting.
After fixing it I get this one that may be actually related to the changes:
****** Resuming failoverSuite. TestZeroSizeIni trd after reboot SetUpTest 0.000s
PASS: <autogenerated>:15: failoverSuite.
snappy list workspace/ snappy/ new_kernel_ file_name/ _integration- tests/tests/ failover_ zero_size_ file_test. go:197: workspace/ snappy/ new_kernel_ file_name/ _integration- tests/tests/ failover_ zero_size_ file_test. go: no such file or directory workspace/ snappy/ new_kernel_ file_name/ _integration- tests/tests/ failover_ zero_size_ file_test. go:142: workspace/ snappy/ new_kernel_ file_name/ _integration- tests/tests/ failover_ zero_size_ file_test. go: no such file or directory a/snappy- selftest- initrd* , 1 expected
Name Date Version Developer
ubuntu-core 2015-09-22 180 ubuntu
generic-amd64 2015-09-22 1.4 canonical
/home/fgimenez/
...open /home/fgimenez/
/home/fgimenez/
...open /home/fgimenez/
... obtained int = 0
... expected int = 1
... 0 files matching /boot/grub/
It seems that after the failover it boots correctly but when tries to revert the changes it tries to do find the modified files in the a partition. If things went good during the setup of the failure this should be the b partition, can you please confirm?